home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
Columbia Kermit
/
kermit.zip
/
newsgroups
/
misc.19941221-19950208
/
000045_news@columbia.edu_Thu Dec 29 00:12:35 1994.msg
< prev
next >
Wrap
Internet Message Format
|
2020-01-01
|
3KB
Received: from apakabar.cc.columbia.edu by watsun.cc.columbia.edu with SMTP id AA06466
(5.65c+CU/IDA-1.4.4/HLK for <kermit.misc@watsun.cc.columbia.edu>); Wed, 28 Dec 1994 19:12:37 -0500
Received: by apakabar.cc.columbia.edu id AA12352
(5.65c+CU/IDA-1.4.4/HLK for kermit.misc@watsun); Wed, 28 Dec 1994 19:12:36 -0500
Path: news.columbia.edu!watsun.cc.columbia.edu!fdc
From: fdc@watsun.cc.columbia.edu (Frank da Cruz)
Newsgroups: comp.protocols.kermit.misc
Subject: Re: kerlite 3.14 beta 16 problem
Date: 29 Dec 1994 00:12:35 GMT
Organization: Columbia University
Lines: 36
Message-Id: <3dsutj$c1u@apakabar.cc.columbia.edu>
References: <y$T0luqcZZCS075yn@primenet.com>
Nntp-Posting-Host: watsun.cc.columbia.edu
Apparently-To: kermit.misc@watsun.cc.columbia.edu
In article <y$T0luqcZZCS075yn@primenet.com>,
Jeff Bishop <jbishop@primenet.com> wrote:
>I have a situation where both people are running kermit 3.14 beta 16. One
>persion starts the transfer on his/her side and the other decides not to
>transfer the file. A series of control-c's are sent with no prevail of
>working at all <GRIN>. The person has to enter kermit and start receiving,
>then cancel using C, why? Are we doing something wrong?
>
No.
>Now, ckermit 190 does cancel with a series of control-c's. Why is msdos
>acting different, or should it not be???
>
It isn't acting different.
A Kermit program can be in either "remote mode" or "local mode". The Local
Kermit is the one that initiated the connection, and the remote one is
the "called" one. The distinction is important because of what happens
with the keyboard and the screen during file transfer. When in local mode,
a Kermit program has access to the keyboard and screen IN ADDITION TO the
communication channel, whereis in remote mode, the "keyboard and screen"
IS the communication channel.
When the remote Kermit is in packet mode, there needs to be a way for the
local user to get it back to command mode "by hand". C-Kermit lets you
do this by typing three consecutive Ctrl-C characters, but only when it is
in remote mode. If it is in local mode, then it has thrown a file transfer
display up on the screen and is sampling the keyboard for special commands.
Well, you get the idea. In the case you describe, BOTH Kermit programs are
in local mode. Neither one is in remote mode, and so neither one is
sensitive to "bare" Control-C characters. Which is as it should be, since
oversensitivity in this area could cause unwanted transfer failures when
there was a lot of noise on the line, etc.
- Frank